Refactor wrapped scan plans so they more user friendly - #2050

This change aims to make the scan syntax much more user friendly. Some examples are show below:

Old syntax

from dodal.plans import wrapped as dpw
>>> RE(dpw.list_grid_scan([], [(x, [1, 5, 10, 50]), (y, [2, 5, 10, 15, 18])]))

>>> RE(dpw.step_grid_scan([], [(x, [1, 10, 1]), (y, [1, 5, 1])]))

# Blueapi client example
>>> bc.plans.step_grid_scan([], [(x, [1, 10, 1]), (y, [1, 5, 1])])

New syntax

>>> RE(dpw.list_grid_scan([], [x, [1, 5, 10, 50], y, [2, 5, 10, 15, 18]]))

>>> RE(dpw.step_grid_scan([], [x, 1, 10, 1, y, 1, 5, 1]))

# Blueapi client example
>>> bc.plans.step_grid_scan([], [x, 1, 10, 1, y, 1, 5, 1])

When BlueAPI supports *args, we can simplifier this even further by removing the final set of brackets:

>>> RE(dpw.step_grid_scan([], x, 1, 10, 1, y, 1, 5, 1))

or BlueAPI client equivalent

>>> bc.plans.step_grid_scan([], x, 1, 10, 1, y, 1, 5, 1)

I've also tried to improve the tests, they now check that the scan shape is correct and checks every custom error message for scan syntax being wrong for step scans.

Instructions to reviewer on how to test:

1. Check implementation and logic is correct
2. Test coverage is sufficient.

Checks for reviewer

• Would the PR title make sense to a scientist on a set of release notes
• If a new device has been added does it follow the standards
• If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
• Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}